Pre-provisioned access management containers for wireless services

ABSTRACT

An enhanced provision of pre-provisioned access management containers for wireless services is disclosed. A method can comprise initiating, by a device comprising a processor, a request for a service from a device of networked devices; facilitating, by the device, a search of an evolved packet core network device for permissive service container data based on the request for the service; facilitating, by the device, retrieval of the permissive service container data from the evolved packet core network device, wherein the permissive service container data comprises code associated with the service; and executing, by the device, the code.

RELATED APPLICATION

The subject patent application is a continuation of, and claims priorityto, U.S. patent application Ser. No. 16/281,615, filed Feb. 21, 2019,and entitled “PRE-PROVISIONED ACCESS MANAGEMENT CONTAINERS FOR WIRELESSSERVICES,” the entirety of which application is hereby incorporated byreference herein.

TECHNICAL FIELD

The disclosed subject matter provides pre-provisioned access managementcontainers for wireless services.

BACKGROUND

Presently, a mobile device has to scan its available bands and selectwith a foreign mobile network operator carrier device for the purpose ofobtaining emergency 911 (E911) service. This can limit enhanced E911services which can require data and/or video feed of a crisis situation,and non-E911 health and welfare traffic from a mobile device user toother users of other mobile devices. Further, the current system canalso complicate or inhibit inter mobile network operator carrier usersupport.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is an illustration of a system that pre-provisions accessmanagement containers for wireless services, in accordance with aspectsof the subject disclosure.

FIG. 2 is a further depiction of a system that pre-provisions accessmanagement containers for wireless services, in accordance with aspectsof the subject disclosure.

FIG. 3 provides illustration of an additional system that pre-provisionsaccess management containers for wireless services, in accordance withaspects of the subject disclosure.

FIG. 4 provides another illustration of a system that pre-provisionsaccess management containers for wireless services, in accordance withaspects of the subject disclosure.

FIG. 5 illustrates another depiction of a system that pre-provisionsaccess management containers for wireless services, in accordance withaspects of the subject disclosure.

FIG. 6 depicts a further system that pre-provisions access managementcontainers for wireless services, in accordance with aspects of thesubject disclosure.

FIG. 7 depicts a another a system that pre-provisions access managementcontainers for wireless services, in accordance with aspects of thesubject disclosure.

FIG. 8 provides illustration of a flow chart or method forpre-provisioning of access management containers for wireless services,in accordance with aspects of the subject disclosure.

FIG. 9 is a block diagram of an example embodiment of a mobile networkplatform to implement and exploit various features or aspects of thesubject disclosure.

FIG. 10 illustrates a block diagram of a computing system operable toexecute the disclosed systems and methods in accordance with anembodiment.

DETAILED DESCRIPTION

The subject disclosure is now described with reference to the drawings,wherein like reference numerals are used to refer to like elementsthroughout. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide a thoroughunderstanding of the subject disclosure. It may be evident, however,that the subject disclosure may be practiced without these specificdetails. In other instances, well-known structures and devices are shownin block diagram form in order to facilitate describing the subjectdisclosure.

The disclosed systems and methods, in accordance with variousembodiments, provide a system, apparatus, or device comprising: aprocessor, and a memory that stores executable instructions that, whenexecuted by the processor, facilitate performance of operations. Theoperations can comprise receiving event trigger data comprising arequest for a service from a user device; initiating a search of a firstevolved packet core network device for permissive service container databased on the request for the service; retrieving the permissive servicecontainer data from the first evolved packet core network device,wherein the permissive service container data comprises code associatedwith the service; downloading the permissive service container to theuser device; and facilitating execution of the code on the user device.

Further operations can comprise determining, based on the event triggerdata, that the user device has transitioned from a second evolved packetcore network to a first evolved packet core network, and wherein thesearch is a first search, initiating, based on the request for theservice, a second search of a second evolved packet core network device.

In accordance with further embodiments, the subject disclosure describesa method and/or process, comprising a series of acts that can include:initiating, by a device comprising a processor, a request for a servicefrom a device of networked devices; facilitating, by the device, asearch of an evolved packet core network device for permissive servicecontainer data based on the request for the service; facilitating, bythe device, retrieval of the permissive service container data from theevolved packet core network device, wherein the permissive servicecontainer data comprises code associated with the service; andexecuting, by the device, the code.

Additional acts can comprise initiating, by the device, the request forthe service based on a transition by the device from a first evolvedpacket core network to a second evolved packet core network.

In accordance with the foregoing, the transition from the first evolvedpacket core network to the second evolved packet core network can bedetermined based on a location area code; the transition from the firstevolved packet core network to the second evolved packet core networkcan be determined based on a tracking area code; the first evolvedpacket core network can be associated with a first unique valuegenerated by a first mobile network operator identity, and/or the secondevolved packet core network can be associated with a second unique valuegenerated by a second mobile network operator identity.

In accordance with still further embodiments, the subject disclosuredescribes a machine readable storage medium, a computer readable storagedevice, or non-transitory machine readable media comprising instructionsthat, in response to execution, cause a computing system comprising atleast one processor to perform operations. The operations can include:receiving event trigger data comprising a request for a service from auser device; initiating a search of a first evolved packet core networkdevice for permissive service container data based on the request forthe service; retrieving the permissive service container data from thefirst evolved packet core network device, wherein the permissive servicecontainer data comprises code associated with the service; downloadingthe permissive service container to the user device; and facilitatingexecution of the code on the user device.

Additional operations can include determining, based on the eventtrigger data, that the user device has transitioned from a secondevolved packet core network to a first evolved packet core network;wherein the search is a first search, initiating, based on the requestfor the service, a second search of a second evolved packet core networkdevice, wherein the permissive service container data is cached to asecond group of evolved packet core network devices.

The subject application details and describes pre-provisioned accessmanagement containers for wireless services that can accelerate serviceto wireless devices, such as smart phones, cellular devices, and thelike, in times of emergency and/or at other times, when severe networkcongestion can be anticipated in regard to non-emergency events, such alive music events, sporting events (e.g., Olympic games, soccer worldcup, rugby world cup, . . . ), political rallies, and the like.

The subject application provides and creates permissive servicecontainers that can be rapidly deployed into a packet core network tocover emergencies and/or special events where cooperation betweenvarious and/or disparate mobile network operator (MNO) carriers can beadvised. In accordance with one or more embodiments, the permissiveservice containers can be loaded or cached into both local and/or one ormore foreign mobile network operators Evolved Packet Core, therebyleveraging concepts such as the open networking automation platform(ONAP)—a platform for real-time, policy-driven orchestration andautomation of physical and virtual network functions that enablessoftware, network, information technology, and cloud providers anddevelopers to rapidly automate new services and support completelifecycle management.

The containers, in one or more embodiments, can be loaded dynamically.In additional and/or alternative embodiments, the containers can remainin a state of stasis, a state of hibernation, or a state of latency,until an event trigger is received or obtained. An event trigger, inaccordance with various disclosed embodiments, can be a location areacode/tracking area code (LAC/TAC) triggering event, wherein thecontainer can be dynamically downloaded to, or retrieved by, a userequipment device/mobile device in response to the mobile device/userequipment device having been determined to have entered (or exited) ageographic area controlled or maintained by a grouping of cellularnetworked devices (e.g., a base station of a distributed network of basestation devices, an eNodeB device comprising a network of eNodeBdevices, an access point device of a cluster of network device, a gNodeBdevice included in a network of gNodeB devices, etc.) associated with aunique externally generated value(s) denoting an assigned geographiclocation area or geographic tracking area within a MNO's network. Theunique externally generated value can generally be generated by one ormore device included in a MNO's Evolved Packet Core network. The eventtrigger can be one that is mandated by law, regulation, reciprocalarrangement, and/or contract between MNOs, and can be determined from adefined or definable package of essential services and/or streaming ofdefined or definable media content for a defined or definable period oftime. Examples of a package of essential services can include 911emergency location services, text services (e.g., simple message service(SMS), multimedia message service (MMS), and the like), voice telephonicservices (e.g., voice over internet protocol (VoIP), voice over longterm evolution (VoLTE), . . . ), streaming of weather warnings bynational weather services, streaming of amber alerts, streaming ofadvisory alerts/messages, . . . .

An advantage for the creation, provision, and/or deployment ofpermissive service containers into a packet core network to coveremergencies and/or special events, wherein various and/or disparate MMOscan collaborate with one another, is that scarce infrastructureresources can be collectively pooled across a panoply of different MNOassociated devices to enhance emergency service coverage and/or optimizecontent delivery. Additionally, creation, provision, and/or deploymentof permissive service containers can better allow individual MNOs toresell services to one another where such resale makes economic and/orpractical sense. Further, deployment and/or use of permissive servicecontainers can also be boon to first responder network authority(FirstNet) users, as the distribution and dissemination of thepermissive service containers can provide another layer of reliabilityto the extant FirstNet system that currently uses, in order: a dedicatedFirstNet infrastructure, overlaid, when necessary, with a first MNOinfrastructure, which in turn can be augmented, when required, withsecond and third disparate MNO infrastructures.

FirstNet system is a legislated radio networkarchitecture/infrastructure providing a nationwide high-speed broadbandwireless network; a single interoperable platform for law enforcement,firefighters, paramedics, and other public safety officials in everystate, county, locality and tribal area in the United States of Americato use during times of emergency and/or crisis. While the subjectdisclosure is described in various embodiments in context of theFirstNet system, those having ordinary skill in the art will becognizant that this disclosure can have a wider applicability thannon-emergency situations.

The disclosed and described permissive container concept, in accordancewith various embodiments, can extend to service stacks such asshared-use protocol stacks like the internet protocol multimediasubsystem (IMS). Typically for example, VoLTE roaming is disabled forbring your own device (BYOD) scenarios because not all services and/orsubsystems included in shared-use protocol stacks necessarily work wellin disparate MNO carrier networks. The rationale for shared-use protocolstacks, such as IMS service stacks, not working in identical mannersacross various MNO carrier networks can be a consequence of disparateand/or divergent implementation of, albeit in full compliance with, thetechnical standards that outline the entirety of the IMS service stack.

The permissive downloadable container disclosed herein proposes acontainer for shared-use protocol stacks. Further, respectivedownloadable containers can also be provided for messaging platforms,secure sockets, special access point networks (APNs) and gateways, etc.

A permissive container in the context of the subject description can bean executable software or data structure (e.g., an abstract data typecomprising groupings of key value pairs) comprising a group of functionsand/or facilities that can allow seamless inter-MNO connectivity andoperability by a user equipment device/mobile device when the userequipment device/mobile device crosses between two disparate MNO carriernetworks. Generally, a permissive container can be a package or wrapperaround an instance of executable software (such as, a grouping ofshared-use protocol services, a group of IMS services (e.g., IMS stack)and/or individual services comprising the group of services—MMS, SMS,VoLTE, . . . ) that includes everything that the executable softwarerequires to execute autonomously, including code, runtime and/or systemtools and/or libraries. The executable software can then be executed ina first MNO carrier network and in a second MNO carrier network, whereinthe first MNO carrier network is a ‘local’ MNO carrier networkenvironment with regard to a user equipment device/mobile device, andthe second MNO carrier network is a ‘foreign’ MNO carrier networkenvironment in the context of the user equipment device/mobile device.

The result of executing the executable software on a first deviceassociated with the first MNO carrier network and executing theexecutable software on a second device associated with the second MNOcarrier network should substantially be the same or similar, so that auser of a mobile device/user device transitioning between the first MNOcarrier network (e.g., the local MNO carrier network) and the second MNOcarrier network (e.g., the foreign MNO carrier network) should be unableto perceive the difference between utilizing a service of a group ofservices associated with the executable software executing on the firstMNO carrier network, and utilizing the service of the group of servicesassociated with the executable software executing on the second MNOcarrier network.

Now with reference to the Figures, FIG. 1 illustrates a system 100 thatprovides pre-provisioned access management containers for wirelessservices. System 100 can include local MNO carrier device 102 that canbe in communication with a local packet core network (e.g., EvolvedPacket Core) and a user equipment device 106 that can be associated withthe local MNO carrier network (e.g., user equipment device 106 is amember of, and associated with, the local packet core network controlledby a MNO carrier). Local MNO carrier device 102 can also be inreciprocal communication, via a foreign packet core network, with aforeign MNO carrier device 104. It will be understood by those skilledin the art that the term “local MNO” can refer to a first MNO and theterm “foreign MNO” can refer to a second MNO, wherein the first MNO andthe second MNO refer to disparate commercial telecommunicationidentities/operators/organizations.

Local MNO carrier device 102 in accordance with various embodiments cancreate, generate, disseminate, and/or cache permissive servicecontainers into the local packet core network as well as the foreignpacket core network. The permissive service containers can leverageconcepts comprising ONAP. The permissive service containers can also beloaded dynamically to either the local packet core network and/or theforeign packet core network.

In accordance with one or more embodiments, the permissive servicecontainers can remain in a state of stasis, a static state, a state ofhibernation, and/or a state of latency in the evolved packet core (e.g.,local evolved packet core and/or foreign packet core) until an eventtrigger is received or obtained from a user device (e.g., user equipmentdevice 106) by a local MNO carrier device (e.g., local MNO carrierdevice 102). The event trigger can, for example, be a location areacode/tracking area code (LAC/TAC) event, wherein the permissive servicecontainers can be dynamically downloaded from, or retrieve by, userequipment device 106 in response to user equipment device 106 havingbeen determined to have entered (or exited) a defined geographical areacontrolled and/or maintained by a device or grouping of devicescomprising a distributed network of devices (e.g., local MNO carrierdevice 102).

Generally, the defined geographical area controlled and/or maintained bya device or grouping of devices comprising the distributed network ofdevices can be assigned and associated with a unique externallygenerated value denoting the defined geographical area. With referenceto the situation depicted in FIG. 1, since user equipment device 106 isassociated with local MNO carrier device 102 (e.g., user equipmentdevice 106 and local MNO carrier device 102 are affiliated with a commoncarrier network), there is typically no need for user equipment device106 to initiate a download of the permissive service containers from thepacket core network (e.g., either local packet core network and/orforeign packet core network) because there should be no discernibledistinction in regard to operation of the shared-use protocol stack onuser equipment device 106 and/or local MNO carrier device 102.

The event trigger can be one that is mandated by law, regulation,reciprocal arrangement between disparate MNOs, and/or contract between acollection of MNOs. The event trigger, in accordance with variousembodiments, can be determined from a package of essential servicesand/or the streaming of media content for a defined or definable periodof time. As noted earlier, examples of a package of essential servicescan include 911 emergency location services, text services, voicetelephonic services, streaming of weather warnings by national weatherauthorities, streaming of amber alerts, and/or streaming of advisoryalerts/messages.

With reference to FIG. 2, illustrated therein is system 100, nowreferenced as system 200, that provides pre-provisioned accessmanagement containers for wireless services. System 200 can includeforeign MNO carrier device 104 that can be in operable communicationwith a foreign packet core network (e.g., Evolved Packet Core) and auser equipment device 106 that can be associated with a local MNOcarrier network (e.g., user equipment device 106 is a member of, andassociated with, the local packet core network controlled by a MNOcarrier) but now is in communication with foreign MNO carrier device104. Additionally, as depicted, foreign MNO carrier device 104 can alsobe in reciprocal communication, via foreign packet core network and/orlocal packet core network, with a local MNO carrier device 102.

As illustrated in the depicted instance, user equipment device 106 canbe served by foreign MNO carrier device 104, wherein foreign MNO carrierdevice 104 provides the IMS stack services to user equipment device 106.However, due to differences of implementation of the shared-use protocolstack by the foreign MNO carrier device 104 with respect to local MNOcarrier device 102, the facilities and/or functionalities associatedwith the shared-use protocol stack as implemented by local MNO carrierdevice 102 and foreign MNO carrier device 104, for use by mobile device106, can differ markedly.

Thus, in order to overcome the differences between the facilities and/orfunctionalities of IMS stack implementations provided by local MNOcarrier device 102 and foreign MNO carrier device 104, in accordancewith one or more embodiments, foreign MNO carrier device 104, inresponse to detecting that user equipment device 106 is not associatedwith the foreign packet core network based, for example, on a triggeringevent, such as a change in LAC/TAC from using functions and/orfacilities associated with local MNO carrier device 102 and the localpacket core network to foreign MNO carrier device 104 and the foreignpacket core network, can determine whether there are any pertinentpermissive service containers (previously persisted to foreign packetcore network by local MNO carrier device 102) in the packet core networkassociated with foreign MNO carrier device 104. In response todetermining that there are pertinent and previously cached permissiveservice containers (for use by devices associated with the packet coresupported by local MNO carrier device 102) in the packet core networkassociated with foreign MNO carrier device 104, foreign MNO carrierdevice 104 can facilitate the downloading of these pertinent permissiveservice container to user equipment device 106.

In accordance with various additional and/or alternative embodiments, ifforeign MNO carrier device 104, in response to detecting that userequipment device 106 is not associated with the foreign packet corenetwork, and determining that there are no pertinent permissive servicecontainers cached to the packet core network associated with foreign MNOcarrier device 104, foreign MNO carrier device 104 can facilitate asearch of the packet core network associated with local MNO carrierdevice 102 to ascertain whether there are extant pertinent andpreviously cached permissive service containers in the packet corenetwork associated with local MNO carrier device 102. Foreign MNOcarrier device 104, in response to determining that the local packetcore network associated with local MNO carrier device 102 includesextant previously cached permissive service containers, can facilitatetransfer of the pertinent permissive service container from the packetcore associated with local MNO carrier device 102 to the packet coreassociated with foreign MNO carrier device 104 and thereafter facilitatethe downloading of these pertinent permissive service container to userequipment device 106. On receiving the permissive service container,user equipment device 106 can execute code included in the permissiveservice container to provide the functionalities and/or facilitiesassociated with the shared-use protocol stack as implemented for devices(e.g., user equipment device 106) that are native to the packet coreassociated with local MNO carrier device 102.

In accordance with yet further embodiments, alternative and/oradditional, where foreign MNO carrier device 104, in response to:detecting that user equipment device 106 is not associated with theforeign packet core network; determining that there are no pertinentpermissive service containers cached to the packet core networkassociated with foreign MNO carrier device 104; and facilitating asearch of the packet core network associated with local MNO carrierdevice 102 and determining that there are no extant pertinent andpreviously cached permissive service containers in the packet corenetwork associated with local MNO carrier device 102, foreign MNOcarrier device 104 can facilitate local MNO carrier device 102 toinitiate creation, generation, and/or distribution/caching (e.g., to thepacket core network associated with local MNO carrier device 102 and/orto the packet core network associated with foreign MNO carrier device104) of the permissive service containers. Once the permissive servicecontainers have been created, generated, and/or distributed/cached tothe packet core network(s) (e.g., packet core network associated withlocal MNO carrier device 102 and/or packet core network associated withforeign MNO carrier device 104), foreign MNO carrier device 104 canfacilitate the downloading of the pertinent permissive service containerto user equipment device 106, whereupon on obtaining the permissiveservice container, user equipment device 106 can execute code includedin the permissive service container to provide the functionalitiesand/or facilities associated with the shared-use protocol stack asimplemented for devices (e.g., user equipment device 106) that arenative to the packet core associated with local MNO carrier device 102.

FIG. 3 illustrates system 100, now referred to as system 300, forproviding pre-provisioned access management containers for wirelessservices. System 300 can include local MNO carrier device 102 that canbe in communication with local packet core network (e.g., Evolved PacketCore). Local MNO carrier device 102, in accordance with variousembodiments, can create, generate, disseminate, and/or cache permissiveservice containers into the local packet core network. As noted earlier,the permissive service containers can be loaded dynamically into thelocal packet core network and/or into a foreign packet core network (notshown).

In accordance with various embodiments, once local MNO carrier device102 has created, generated, disseminated, and/or cached the permissiveservice containers, the permissive service containers can remain in astate of stasis, a state of hibernation, and/or a state of latencywithin the local packet core network and/or in the foreign packet corenetwork until such time as they are required by user devices associatedwith either local packet core network and/or the foreign packet corenetwork.

FIG. 4 depicts system 100, now referred to as system 400, for theprovision of pre-provisioned access management containers for wirelessservices. System 400 can include foreign MNO carrier device 104 that canbe in communication with foreign packet core network (e.g., EvolvedPacket Core). Foreign MNO carrier device 104, in accordance with variousembodiments, can determine, based on one or more triggering event suchas a change in LAC/TAC, whether or not a user device (e.g., userequipment device 106) is not affiliated with aspects of the foreignpacket core network. Further foreign MNO carrier device 104 can alsodetermine whether or not there are any permissive services containers(previously persisted to the foreign packet core network by local MNOcarrier device 102) in the packet core network associated with foreignMNO carrier device 104. In response to determining that there arepertinent and previously cached permissive service containers in thepacket core network associated with foreign MNO carrier device 104,foreign MNO carrier device 104 can facilitate downloading of thesepertinent permissive service containers to the user device.

In accordance with additional and/or alternative embodiments, shouldforeign MNO carrier device 104, in response to detecting that a userdevice is not associated with the foreign packet core network, andfurther determining that there are no pertinent permissive servicecontainers cached to the packet core network associated with foreign MNOcarrier device 104, foreign MNO carrier device 104 can facilitate asearch of the packet core network associated with local MNO carrierdevice 102 to ascertain whether or not there are pertinent andpreviously cached permissive service containers in the packet corenetwork associated with local MNO carrier device 102. Foreign MNOcarrier device 104, in response to determining that the packet corenetwork associated with local MNO carrier device 102 includes extantpreviously cached permissive service containers, can facilitate transferof the pertinent permissive service containers from the packet corenetwork associated with local MNO carrier device 102 to the packet corenetwork associated with foreign carrier device 104, and thereafter canfacilitate the downloading of these pertinent permissive servicecontainers to the user device. On receiving the permissive servicecontainers, the user device can execute code included in the permissiveservice condensers to provide the functionalities and/or facilitiesassociated with one or more service included in the shared-use protocolstack as implemented for devices that are native to, or affiliated with,the packet core network associated with local MNO carrier device 102.

In accordance with additional varied embodiments, where foreign MNOcarrier device 104, in response to: detecting that a user device is notassociated or affiliated with the foreign packet core network;determining that there are no pertinent permissive service containercached to the packet core network associated with foreign MNO carrierdevice 104; and subsequent to facilitating a search of the packet corenetwork associated with local MNO carrier device 102 and determiningthat there are no extant pertinent and previously cached permissiveservice containers in the packet core network associated with local MNOcarrier device 102, foreign MNO carrier device 104 can facilitate localMNO carrier device 102 to initiate creation, generation, and/ordistribution/caching of the permissive service containers to the packetcore network associated with local MNO carrier device 102 and/or to thepacket core network associated with foreign MNO carrier device 104.

Once the permissive service containers have been created, generated,and/or cached to the packet core network(s), foreign MNO carrier device104 can facilitate the downloading of the pertinent permissive servicecontainers to the user device, whereupon on obtaining the permissiveservice containers, the user device can execute code included in thepermissive service containers to provide one or more functionalityand/or facility associated with services included in the shared-useprotocol stack, as the shared-use protocol stack has been implementedfor devices that are affiliated with the packet core network associatedwith local MNO carrier device 102.

FIG. 5 provides further depiction of local MNO carrier device 102, nowlabeled as system 500, for providing pre-provisioned access managementcontainers for wireless services. Local MNO carrier device 102 caninclude container engine 502 that can be coupled to processor 504,memory 506, and storage 508. Container engine 502 can be incommunication with processor 504 for facilitating operation of computeror machine executable instructions and/or components by container engine502, memory 506 for storing data and/or the computer or machineexecutable instructions and/or components, and storage 508 for providinglonger term storage of data and/or machine and/or computer readableinstructions. Additionally, local MNO carrier device 102 can receiveinput 510 for use, manipulation, and/or transformation by containerengine 502 to produce one or more useful, concrete, and tangible result,and/or transform one or more articles to different states or things.Further, local MNO carrier device 102 can generate and output theuseful, concrete, and tangible results and/or the transformed one ormore articles produced by container engine 502 as output 512.

Container engine 502 at the instigation, for example, of foreign MNOcarrier device 104, can initiate creation, generation, and/ordistribution/caching of the permissive service containers to both thepacket core network associated with local MNO carrier device 102 as wellas to the packet core network associated with foreign MNO carrier device104. The permissive service containers, after being propagated andcached to the packet core networks associated with local MNO carrierdevice 102 and/or foreign MNO carrier device 104, can thereafter be usedby one or more user devices that are not currently operating withintheir native local packet core network (e.g., the user device is beingoperated in a non-native foreign packet core network) to execute codeincluded in the permissive service containers to provide one or morefunctionality and/or facility associated with services included in anshared-use protocol stack as if the shared-use protocol stack had beenimplemented for devices that are affiliated with their home packet corenetwork.

FIG. 6 illustrates foreign MNO carrier device 104, now labeled as system600, for providing pre-provisioned access management containers forwireless services. Foreign MNO carrier device 104 can include downloadengine 602 that can be coupled to processor 604, memory 606, and storage608. Download engine 602 can be in communication with processor 604 forfacilitating operation of computer or machine executable instructionsand/or components by download engine 602, memory 606 for storing dataand/or the computer or machine executable instructions and/orcomponents, and storage 608 for providing longer term storage of dataand/or machine and/or computer readable instructions. Additionally,foreign MNO carrier device 104 can receive input 610 for use,manipulation, and/or transformation by download engine 602 to produceone or more useful, concrete, and tangible result, and/or transform oneor more articles to different states or things. Further, foreign MNOcarrier device 104 can generate and output the useful, concrete, andtangible results and/or the transformed one or more articles produced bydownload engine 602 as output 612.

Download engine 602, in accordance with one or more embodiments, candetect whether or not a user device (e.g., user equipment device 106) isa member of a local/native evolved packet core network or a member of aforeign/non-native packet core network. Determination of whether or nota user device is a member of a local/native evolved packet core networkor a foreign/non-native evolved packet core network can be based on atriggering event, such as whether the user device has transitionedbetween disparate LAC/TAC defined geographical areas.

Where download engine 602 determines that the user device is a member ofa foreign/non-native evolved packet core network, download engine 602can facilitate determining whether or not there are any pertinentpermissive service containers cached to the packet core networkassociated with foreign MNO carrier device 104. Download engine 602 canalso, where it is ascertained that there are no pertinent permissiveservice containers cached to the packet core network associated withforeign MNO carrier device 104, facilitate a search of the packet corenetwork associated with local MNO carrier device 102. Where downloadengine 602 determines that the packet core network associated with localMNO carrier device 102 includes extant previously cached permissiveservice containers, download engine 602 can facilitate transfer of thepertinent permissive service containers from the packet core networkassociated with local MNO carrier device 102 to the packet core networkassociated with foreign MNO carrier device 104, and thereafter caninitiate and/or facilitate downloading the retrieved permissive servicecontainers to the user device. At has been noted earlier, once the userdevice has obtained the permissive service container the user device canexecute code included in the permissive service container to releasefunctionalities and/or facilities associated with services comprisingthe shared-use protocol stack as implemented for devices that are nativeto the packet core associated with local MNO carrier device 102.

Download engine 602, where it is determined that a user device is notassociated with the packet core network associated with foreign MNOcarrier device 104; that there are no pertinent permissive servicecontainers cached to the packet core network associated with foreign MNOcarrier device 104 and that there are no extant pertinent and previouslycached permissive service containers in the packet core networkassociated with local MNO carrier device 102, can facilitate local MNOcarrier device 102 to create, generate, and/or distribute/cache thepermissive service containers to the packet core network associated withlocal MNO carrier device 102 and/or the packet core network associatedwith foreign MNO carrier device 104. Once the permissive servicecontainers have been created, generated, and/or disseminated/cached tothe packet core network(s), download engine 602 can facilitate thedownloading of the permissive service containers to the user device.

FIG. 7 illustrates user equipment device 106, now labeled as system 700,for providing pre-provisioned access management containers for wirelessservices. User equipment device 106 can include trigger engine 702 thatcan be coupled to processor 704, memory 706, and storage 708. Triggerengine 702 can be in communication with processor 704 for facilitatingoperation of computer or machine executable instructions and/orcomponents by trigger engine 702, memory 706 for storing data and/or thecomputer or machine executable instructions and/or components, andstorage 708 for providing longer term storage of data and/or machineand/or computer readable instructions. Additionally, user equipmentdevice can receive input 710 for use, manipulation, and/ortransformation by trigger engine 702 to produce one or more useful,concrete, and tangible result, and/or transform one or more articles todifferent states or things. Further, user equipment device 106 cangenerate and output the useful, concrete, and tangible results and/orthe transformed one or more articles produced by trigger engine 702 asoutput 712.

Trigger component 702 can be used by user equipment device 106 duringtimes of emergency and/or crisis, and/or when user equipment device 106is not available for reasons such as a declared emergency, when a groupof MNOs collaborate to support a large event (e.g., sporting event,musical concert event, . . . ). During such a declared emergency or whenMNOs collaborate to support a large event, trigger component 702 canattempt to establish communication with a foreign MNO carrier device(e.g., foreign MNO carrier device 104) in order to obtain one of moreservices included in the IMS stack. As has been observed earlier,shared-use protocol stack implementations can vary markedly between thepacket core networks of the various MNOs. For example, a first packetcore network associated with a first MNO can have implemented servicesA, B, and C from the shared-use protocol stack, whereas a second packetcore network associated with a second MNO can have only implementedservices A, C, and D. Thus, when user equipment device 106 moves fromthe first packet core network to the second packet core network, thesecond packet core network would not be able to support the services(e.g., A, B, and C) the user equipment device 106 would expect toexperience in its native operating environment (e.g., the first packetcore network). To surmount this issue therefore, when trigger engine 702determines that user equipment device 106 has crossed into a servicecoverage area supported by a foreign packet core network it can contacta MNO carrier device (e.g., foreign MNO carrier device 104) to obtainservices included in the shared-use protocol stack. In this instance,the MNO carrier device will detect that the request emanating from userequipment device 106 comprising trigger engine 702 is from a user devicethat is not affiliated with the packet core network for which the MNOcarrier device is responsible. The MNO carrier device with thus need tolocate from the packet core network (e.g., local packet core networkassociated with local MNO carrier device 102 and/or foreign packet corenetwork associated with foreign MNO carrier device 104) and thereafterfacilitate a download of permissive service containers to the userequipment device. On receiving the permissive service containers,trigger engine 702 can execute the code that can be included in thepermissive service containers to provide the functionalities and/orfacilities associated with the IMS stack as implemented for devices thatare native to the packet core associated with local packet core network(e.g., local packet core network affiliated with local MNO carrierdevice 102).

In view of the example system(s) described above, example method(s) thatcan be implemented in accordance with the disclosed subject matter canbe better appreciated with reference to the flow charts in FIG. 8. Forpurposes of simplicity of explanation, example method disclosed hereinis presented and described as a series of acts; however, it is to beunderstood and appreciated that the disclosure is not limited by theorder of acts, as some acts may occur in different orders and/orconcurrently with other acts from that shown and described herein. Forexample, one or more example methods disclosed herein couldalternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, interaction diagram(s) mayrepresent methods in accordance with the disclosed subject matter whendisparate entities enact disparate portions of the methods. Furthermore,not all illustrated acts may be required to implement a describedexample method in accordance with the subject specification. Furtheryet, the disclosed example method can be implemented in combination withone or more other methods, to accomplish one or more aspects hereindescribed. It should be further appreciated that the example methoddisclosed throughout the subject specification are capable of beingstored on an article of manufacture (e.g., a computer-readable medium)to allow transporting and transferring such methods to computers forexecution, and thus implementation, by a processor or for storage in amemory.

FIG. 8 illustrates a method 800 for providing pre-provisioned accessmanagement containers for wireless services. Method 800 can commence atact 802 wherein, system 700 (e.g., trigger engine 702), can contact aMNO carrier device (e.g., local MNO carrier device 102 or foreign MNOcarrier device 104) for shared-use protocol stack data (e.g., IMS stackdata). The shared-use protocol stack data can be data for one or moreshared-use protocol stack service such as VoLTE, VOIP, SMS, MMS,streaming audio and/or visual content, emergency alert data, amber alertdata, weather warning data, and the like. At 804 trigger device 702 canbe placed in a hibernation state until the MNO carrier device locatesand downloads a permissive container comprising the requested shared-useprotocol stack data to memory 706 and/or storage 708. At 806 triggerengine 702 in response to receiving the permissive container, triggerengine 702 in conjunction with processor 704 can execute code includedin the permissive container to provide a facility or functionalityassociated with the requested shared-use protocol stack data.

It should be realized and appreciated by those of ordinary skill, theforegoing non-limiting example use application(s) are merelyillustrations of a use to which the disclosed and described solution canbe applied and thus are provided solely for the purposes of exposition.The described and disclosed subject matter is therefore not limited tothe foregoing example application(s), but can find applicability inother more generalized circumstances and use applications.

FIG. 9 presents an example embodiment 900 of a mobile network platform910 that can implement and exploit one or more aspects of the disclosedsubject matter described herein. Generally, wireless network platform910 can include components, e.g., nodes, gateways, interfaces, servers,or disparate platforms, that facilitate both packet-switched (PS) (e.g.,internet protocol (IP), frame relay, asynchronous transfer mode (ATM))and circuit-switched (CS) traffic (e.g., voice and data), as well ascontrol generation for networked wireless telecommunication. As anon-limiting example, wireless network platform 910 can be included intelecommunications carrier networks, and can be considered carrier-sidecomponents as discussed elsewhere herein. Mobile network platform 910includes CS gateway node(s) 912 which can interface CS traffic receivedfrom legacy networks like telephony network(s) 940 (e.g., publicswitched telephone network (PSTN), or public land mobile network (PLMN))or a signaling system #7 (SS7) network 970. Circuit switched gatewaynode(s) 912 can authorize and authenticate traffic (e.g., voice) arisingfrom such networks. Additionally, CS gateway node(s) 912 can accessmobility, or roaming, data generated through SS7 network 960; forinstance, mobility data stored in a visited location register (VLR),which can reside in memory 930. Moreover, CS gateway node(s) 912interfaces CS-based traffic and signaling and PS gateway node(s) 918. Asan example, in a 3GPP UMTS network, CS gateway node(s) 912 can berealized at least in part in gateway GPRS support node(s) (GGSN). Itshould be appreciated that functionality and specific operation of CSgateway node(s) 912, PS gateway node(s) 918, and serving node(s) 916, isprovided and dictated by radio technology(ies) utilized by mobilenetwork platform 910 for telecommunication.

In addition to receiving and processing CS-switched traffic andsignaling, PS gateway node(s) 918 can authorize and authenticatePS-based data sessions with served mobile devices. Data sessions caninclude traffic, or content(s), exchanged with networks external to thewireless network platform 910, like wide area network(s) (WANs) 950,enterprise network(s) 970, and service network(s) 980, which can beembodied in local area network(s) (LANs), can also be interfaced withmobile network platform 910 through PS gateway node(s) 918. It is to benoted that WANs 950 and enterprise network(s) 970 can embody, at leastin part, a service network(s) like IP multimedia subsystem (IMS). Basedon radio technology layer(s) available in technology resource(s) 917,packet-switched gateway node(s) 918 can generate packet data protocolcontexts when a data session is established; other data structures thatfacilitate routing of packetized data also can be generated. To thatend, in an aspect, PS gateway node(s) 918 can include a tunnel interface(e.g., tunnel termination gateway (TTG) in 3GPP UMTS network(s) (notshown)) which can facilitate packetized communication with disparatewireless network(s), such as Wi-Fi networks.

In embodiment 900, wireless network platform 910 also includes servingnode(s) 916 that, based upon available radio technology layer(s) withintechnology resource(s) 917, convey the various packetized flows of datastreams received through PS gateway node(s) 918. It is to be noted thatfor technology resource(s) 917 that rely primarily on CS communication,server node(s) can deliver traffic without reliance on PS gatewaynode(s) 918; for example, server node(s) can embody at least in part amobile switching center. As an example, in a 3GPP UMTS network, servingnode(s) 916 can be embodied in serving GPRS support node(s) (SGSN).

For radio technologies that exploit packetized communication, server(s)914 in wireless network platform 910 can execute numerous applicationsthat can generate multiple disparate packetized data streams or flows,and manage (e.g., schedule, queue, format . . . ) such flows. Suchapplication(s) can include add-on features to standard services (forexample, provisioning, billing, customer support . . . ) provided bywireless network platform 910. Data streams (e.g., content(s) that arepart of a voice call or data session) can be conveyed to PS gatewaynode(s) 918 for authorization/authentication and initiation of a datasession, and to serving node(s) 916 for communication thereafter. Inaddition to application server, server(s) 914 can include utilityserver(s), a utility server can include a provisioning server, anoperations and maintenance server, a security server that can implementat least in part a certificate authority and firewalls as well as othersecurity mechanisms, and the like. In an aspect, security server(s)secure communication served through wireless network platform 910 toensure network's operation and data integrity in addition toauthorization and authentication procedures that CS gateway node(s) 912and PS gateway node(s) 918 can enact. Moreover, provisioning server(s)can provision services from external network(s) like networks operatedby a disparate service provider; for instance, WAN 950 or GlobalPositioning System (GPS) network(s) (not shown). Provisioning server(s)can also provision coverage through networks associated to wirelessnetwork platform 910 (e.g., deployed and operated by the same serviceprovider), such as femto-cell network(s) (not shown) that enhancewireless service coverage within indoor confined spaces and offloadradio access network resources in order to enhance subscriber serviceexperience within a home or business environment by way of UE 975.

It is to be noted that server(s) 914 can include one or more processorsconfigured to confer at least in part the functionality of macro networkplatform 910. To that end, the one or more processor can execute codeinstructions stored in memory 930, for example. It is should beappreciated that server(s) 914 can include a content manager 915, whichoperates in substantially the same manner as described hereinbefore.

In example embodiment 900, memory 930 can store information related tooperation of wireless network platform 910. Other operationalinformation can include provisioning information of mobile devicesserved through wireless platform network 910, subscriber databases;application intelligence, pricing schemes, e.g., promotional rates,flat-rate programs, couponing campaigns; technical specification(s)consistent with telecommunication protocols for operation of disparateradio, or wireless, technology layers; and so forth. Memory 930 can alsostore information from at least one of telephony network(s) 940, WAN950, enterprise network(s) 970, or SS7 network 960. In an aspect, memory930 can be, for example, accessed as part of a data store component oras a remotely connected memory store.

In order to provide a context for the various aspects of the disclosedsubject matter, FIG. 10, and the following discussion, are intended toprovide a brief, general description of a suitable environment in whichthe various aspects of the disclosed subject matter can be implemented.While the subject matter has been described above in the general contextof computer-executable instructions of a computer program that runs on acomputer and/or computers, those skilled in the art will recognize thatthe disclosed subject matter also can be implemented in combination withother program modules. Generally, program modules include routines,programs, components, data structures, etc. that perform particulartasks and/or implement particular abstract data types.

In the subject specification, terms such as “store,” “storage,” “datastore,” data storage,” “database,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It will be appreciatedthat the memory components described herein can be either volatilememory or nonvolatile memory, or can include both volatile andnonvolatile memory, by way of illustration, and not limitation, volatilememory 1020 (see below), non-volatile memory 1022 (see below), diskstorage 1024 (see below), and memory storage 1046 (see below). Further,nonvolatile memory can be included in read only memory (ROM),programmable ROM (PROM), electrically programmable ROM (EPROM),electrically erasable ROM (EEPROM), or flash memory. Volatile memory caninclude random access memory (RAM), which acts as external cache memory.By way of illustration and not limitation, RAM is available in manyforms such as synchronous RAM (SRAM), dynamic RAM (DRAM), synchronousDRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM(ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM).Additionally, the disclosed memory components of systems or methodsherein are intended to comprise, without being limited to comprising,these and any other suitable types of memory.

Moreover, it will be noted that the disclosed subject matter can bepracticed with other computer system configurations, includingsingle-processor or multiprocessor computer systems, mini-computingdevices, mainframe computers, as well as personal computers, hand-heldcomputing devices (e.g., PDA, phone, watch, tablet computers, netbookcomputers, . . . ), microprocessor-based or programmable consumer orindustrial electronics, and the like. The illustrated aspects can alsobe practiced in distributed computing environments where tasks areperformed by remote processing devices that are linked through acommunications network; however, some if not all aspects of the subjectdisclosure can be practiced on stand-alone computers. In a distributedcomputing environment, program modules can be located in both local andremote memory storage devices.

FIG. 10 illustrates a block diagram of a computing system 1000 operableto execute the disclosed systems and methods in accordance with anembodiment. Computer 1012, which can be, for example, part of thehardware of system 100, includes a processing unit 1014, a system memory1016, and a system bus 1018. System bus 1018 couples system componentsincluding, but not limited to, system memory 1016 to processing unit1014. Processing unit 1014 can be any of various available processors.Dual microprocessors and other multiprocessor architectures also can beemployed as processing unit 1014.

System bus 1018 can be any of several types of bus structure(s)including a memory bus or a memory controller, a peripheral bus or anexternal bus, and/or a local bus using any variety of available busarchitectures including, but not limited to, Industrial StandardArchitecture (ISA), Micro-Channel Architecture (MSA), Extended ISA(EISA), Intelligent Drive Electronics, VESA Local Bus (VLB), PeripheralComponent Interconnect (PCI), Card Bus, Universal Serial Bus (USB),Advanced Graphics Port (AGP), Personal Computer Memory CardInternational Association bus (PCMCIA), Firewire (IEEE 1194), and SmallComputer Systems Interface (SCSI).

System memory 1016 can include volatile memory 1020 and nonvolatilememory 1022. A basic input/output system (BIOS), containing routines totransfer information between elements within computer 1012, such asduring start-up, can be stored in nonvolatile memory 1022. By way ofillustration, and not limitation, nonvolatile memory 1022 can includeROM, PROM, EPROM, EEPROM, or flash memory. Volatile memory 1020 includesRAM, which acts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as SRAM, dynamic RAM(DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM),enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), Rambus direct RAM(RDRAM), direct Rambus dynamic RAM (DRDRAM), and Rambus dynamic RAM(RDRAM).

Computer 1012 can also include removable/non-removable,volatile/non-volatile computer storage media. FIG. 10 illustrates, forexample, disk storage 1024. Disk storage 1024 includes, but is notlimited to, devices like a magnetic disk drive, floppy disk drive, tapedrive, flash memory card, or memory stick. In addition, disk storage1024 can include storage media separately or in combination with otherstorage media including, but not limited to, an optical disk drive suchas a compact disk ROM device (CD-ROM), CD recordable drive (CD-R Drive),CD rewritable drive (CD-RW Drive) or a digital versatile disk ROM drive(DVD-ROM). To facilitate connection of the disk storage devices 1024 tosystem bus 1018, a removable or non-removable interface is typicallyused, such as interface 1026.

Computing devices typically include a variety of media, which caninclude computer-readable storage media or communications media, whichtwo terms are used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media can include,but are not limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disk (DVD) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or other tangible media which can beused to store desired information. In this regard, the term “tangible”herein as may be applied to storage, memory or computer-readable media,is to be understood to exclude only propagating intangible signals perse as a modifier and does not relinquish coverage of all standardstorage, memory or computer-readable media that are not only propagatingintangible signals per se. In an aspect, tangible media can includenon-transitory media wherein the term “non-transitory” herein as may beapplied to storage, memory or computer-readable media, is to beunderstood to exclude only propagating transitory signals per se as amodifier and does not relinquish coverage of all standard storage,memory or computer-readable media that are not only propagatingtransitory signals per se. For the avoidance of doubt, the term“computer-readable storage device” is used and defined herein to excludetransitory media. Computer-readable storage media can be accessed by oneor more local or remote computing devices, e.g., via access requests,queries or other data retrieval protocols, for a variety of operationswith respect to the information stored by the medium.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and includes any information deliveryor transport media. The term “modulated data signal” or signals refersto a signal that has one or more of its characteristics set or changedin such a manner as to encode information in one or more signals. By wayof example, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

It can be noted that FIG. 10 describes software that acts as anintermediary between users and computer resources described in suitableoperating environment 1000. Such software includes an operating system1028. Operating system 1028, which can be stored on disk storage 1024,acts to control and allocate resources of computer system 1012. Systemapplications 1030 take advantage of the management of resources byoperating system 1028 through program modules 1032 and program data 1034stored either in system memory 1016 or on disk storage 1024. It is to benoted that the disclosed subject matter can be implemented with variousoperating systems or combinations of operating systems.

A user can enter commands or information into computer 1012 throughinput device(s) 1036. As an example, mobile device and/or portabledevice can include a user interface embodied in a touch sensitivedisplay panel allowing a user to interact with computer 1012. Inputdevices 1036 include, but are not limited to, a pointing device such asa mouse, trackball, stylus, touch pad, keyboard, microphone, joystick,game pad, satellite dish, scanner, TV tuner card, digital camera,digital video camera, web camera, cell phone, smartphone, tabletcomputer, etc. These and other input devices connect to processing unit1014 through system bus 1018 by way of interface port(s) 1038. Interfaceport(s) 1038 include, for example, a serial port, a parallel port, agame port, a universal serial bus (USB), an infrared port, a Bluetoothport, an IP port, or a logical port associated with a wireless service,etc. Output device(s) 1040 use some of the same type of ports as inputdevice(s) 1036.

Thus, for example, a USB port can be used to provide input to computer1012 and to output information from computer 1012 to an output device1040. Output adapter 1042 is provided to illustrate that there are someoutput devices 1040 like monitors, speakers, and printers, among otheroutput devices 1040, which use special adapters. Output adapters 1042include, by way of illustration and not limitation, video and soundcards that provide means of connection between output device 1040 andsystem bus 1018. It should be noted that other devices and/or systems ofdevices provide both input and output capabilities such as remotecomputer(s) 1044.

Computer 1012 can operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer(s)1044. Remote computer(s) 1044 can be a personal computer, a server, arouter, a network PC, cloud storage, cloud service, a workstation, amicroprocessor based appliance, a peer device, or other common networknode and the like, and typically includes many or all of the elementsdescribed relative to computer 1012.

For purposes of brevity, only a memory storage device 1046 isillustrated with remote computer(s) 1044. Remote computer(s) 1044 islogically connected to computer 1012 through a network interface 1048and then physically connected by way of communication connection 1050.Network interface 1048 encompasses wire and/or wireless communicationnetworks such as local-area networks (LAN) and wide-area networks (WAN).LAN technologies include Fiber Distributed Data Interface (FDDI), CopperDistributed Data Interface (CDDI), Ethernet, Token Ring and the like.WAN technologies include, but are not limited to, point-to-point links,circuit-switching networks like Integrated Services Digital Networks(ISDN) and variations thereon, packet switching networks, and DigitalSubscriber Lines (DSL). As noted below, wireless technologies may beused in addition to or in place of the foregoing.

Communication connection(s) 1050 refer(s) to hardware/software employedto connect network interface 1048 to bus 1018. While communicationconnection 1050 is shown for illustrative clarity inside computer 1012,it can also be external to computer 1012. The hardware/software forconnection to network interface 1048 can include, for example, internaland external technologies such as modems, including regular telephonegrade modems, cable modems and DSL modems, ISDN adapters, and Ethernetcards.

The above description of illustrated embodiments of the subjectdisclosure, including what is described in the Abstract, is not intendedto be exhaustive or to limit the disclosed embodiments to the preciseforms disclosed. While specific embodiments and examples are describedherein for illustrative purposes, various modifications are possiblethat are considered within the scope of such embodiments and examples,as those skilled in the relevant art can recognize.

In this regard, while the disclosed subject matter has been described inconnection with various embodiments and corresponding Figures, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor may also be implemented as acombination of computing processing units.

In the subject specification, terms such as “store,” “storage,” “datastore,” data storage,” “database,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It will be appreciatedthat the memory components described herein can be either volatilememory or nonvolatile memory, or can include both volatile andnonvolatile memory.

As used in this application, the terms “component,” “system,”“platform,” “layer,” “selector,” “interface,” and the like are intendedto refer to a computer-related entity or an entity related to anoperational apparatus with one or more specific functionalities, whereinthe entity can be either hardware, a combination of hardware andsoftware, software, or software in execution. As an example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration and not limitation, both anapplication running on a server and the server can be a component. Oneor more components may reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media, device readablestorage devices, or machine readable media having various datastructures stored thereon. The components may communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems via the signal). Asanother example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, which is operated by a software or firmwareapplication executed by a processor, wherein the processor can beinternal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can include a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

Moreover, terms like “user equipment (UE),” “mobile station,” “mobile,”subscriber station,” “subscriber equipment,” “access terminal,”“terminal,” “handset,” and similar terminology, refer to a wirelessdevice utilized by a subscriber or user of a wireless communicationservice to receive or convey data, control, voice, video, sound, gaming,or substantially any data-stream or signaling-stream. The foregoingterms are utilized interchangeably in the subject specification andrelated drawings. Likewise, the terms “access point (AP),” “basestation,” “NodeB,” “evolved Node B (eNodeB),” “home Node B (HNB),” “homeaccess point (HAP),” “cell device,” “sector,” “cell,” and the like, areutilized interchangeably in the subject application, and refer to awireless network component or appliance that serves and receives data,control, voice, video, sound, gaming, or substantially any data-streamor signaling-stream to and from a set of subscriber stations or providerenabled devices. Data and signaling streams can include packetized orframe-based flows.

Additionally, the terms “core-network”, “core”, “core carrier network”,“carrier-side”, or similar terms can refer to components of atelecommunications network that typically provides some or all ofaggregation, authentication, call control and switching, charging,service invocation, or gateways. Aggregation can refer to the highestlevel of aggregation in a service provider network wherein the nextlevel in the hierarchy under the core nodes is the distribution networksand then the edge networks. UEs do not normally connect directly to thecore networks of a large service provider but can be routed to the coreby way of a switch or radio area network. Authentication can refer todeterminations regarding whether the user requesting a service from thetelecom network is authorized to do so within this network or not. Callcontrol and switching can refer determinations related to the futurecourse of a call stream across carrier equipment based on the callsignal processing. Charging can be related to the collation andprocessing of charging data generated by various network nodes. Twocommon types of charging mechanisms found in present day networks can beprepaid charging and postpaid charging. Service invocation can occurbased on some explicit action (e.g. call transfer) or implicitly (e.g.,call waiting). It is to be noted that service “execution” may or may notbe a core network functionality as third party network/nodes may takepart in actual service execution. A gateway can be present in the corenetwork to access other networks. Gateway functionality can be dependenton the type of the interface with another network.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“prosumer,” “agent,” and the like are employed interchangeablythroughout the subject specification, unless context warrants particulardistinction(s) among the terms. It should be appreciated that such termscan refer to human entities or automated components (e.g., supportedthrough artificial intelligence, as through a capacity to makeinferences based on complex mathematical formalisms), that can providesimulated vision, sound recognition and so forth.

Aspects, features, or advantages of the subject matter can be exploitedin substantially any, or any, wired, broadcast, wirelesstelecommunication, radio technology or network, or combinations thereof.Non-limiting examples of such technologies or networks include Geocasttechnology; broadcast technologies (e.g., sub-Hz, ELF, VLF, LF, MF, HF,VHF, UHF, SHF, THz broadcasts, etc.); Ethernet; X.25; powerline-typenetworking (e.g., PowerLine AV Ethernet, etc.); femto-cell technology;Wi-Fi; Worldwide Interoperability for Microwave Access (WiMAX); EnhancedGeneral Packet Radio Service (Enhanced GPRS); Third GenerationPartnership Project (3GPP or 3G) Long Term Evolution (LTE); 3GPPUniversal Mobile Telecommunications System (UMTS) or 3GPP UMTS; ThirdGeneration Partnership Project 2 (3GPP2) Ultra Mobile Broadband (UMB);High Speed Packet Access (HSPA); High Speed Downlink Packet Access(HSDPA); High Speed Uplink Packet Access (HSUPA); GSM Enhanced DataRates for GSM Evolution (EDGE) Radio Access Network (RAN) or GERAN; UMTSTerrestrial Radio Access Network (UTRAN); or LTE Advanced.

What has been described above includes examples of systems and methodsillustrative of the disclosed subject matter. It is, of course, notpossible to describe every combination of components or methods herein.One of ordinary skill in the art may recognize that many furthercombinations and permutations of the disclosure are possible.Furthermore, to the extent that the terms “includes,” “has,”“possesses,” and the like are used in the detailed description, claims,appendices and drawings such terms are intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim.

What is claimed is:
 1. Network equipment, comprising: a processor; and amemory that stores executable instructions that, when executed by theprocessor, facilitate performance of operations, comprising: receiving,from a user equipment, event trigger data comprising a request for aservice; determining that the user equipment is in a first core networkenvironment; and sending, to the user equipment, code representative ofthe service to be executed on the user equipment, wherein the code is animplementation of the service operational within a second core networkenvironment.
 2. The network equipment of claim 1, wherein the operationsfurther comprise determining the service based on a defined package ofservices selected in accordance with agreement data representative of areciprocal agreement between a first mobile network operator entity anda second mobile network operator entity.
 3. The network equipment ofclaim 1, wherein the operations further comprise, based on the requestfor the service, initiating a search of the first core networkenvironment for permissive service container data.
 4. The networkequipment of claim 3, wherein the operations further comprise obtaining,from the first core network environment, the permissive servicecontainer data, wherein the permissive service container data comprisesthe code representative of the service.
 5. The network equipment ofclaim 3, wherein the operations further comprise downloading thepermissive service container data to the user equipment.
 6. The networkequipment of claim 3, wherein the permissive service container data iscached to a group of evolved packet core network equipment.
 7. Thenetwork equipment of claim 1, wherein the operations further comprisedetermining, based on the event trigger data, that the user equipmenthas transitioned from the second core network environment to the firstcore network environment.
 8. The network equipment of claim 1, whereinthe service is a shared-use protocol stack service.
 9. The networkequipment of claim 1, wherein the service is a multimedia messagingservice.
 10. The network equipment of claim 1, wherein the service is ashort messaging service.
 11. The network equipment of claim 1, whereinthe service is an audio streaming service.
 12. The network equipment ofclaim 1, wherein the service is a streaming of video content associatedwith an emergency event.
 13. The network equipment of claim 1, whereinthe operations further comprise initiating, based on the request for theservice, a search of the second network core environment.
 14. A method,comprising: initiating, by a device comprising a processor, a requestfor a service from a group of network equipment; determining, by thedevice, that the device is associated with a first core network; andexecuting, by the device, code representative of the service, whereinthe code is an instantiation of the service operational within networkequipment of a second core network.
 15. The method of claim 14, furthercomprising identifying, by the device, the service from a collection ofstreaming media data.
 16. The method of claim 15, wherein the networkequipment is second network equipment, and wherein the streaming mediadata is determined based on agreement data representative of anagreement between a first entity controlling first network equipment ofthe first core network and a second entity controlling the secondnetwork equipment of the second core network.
 17. The method of claim14, further comprising retrieving, by the device and from the first corenetwork, permissive service data comprising the code representative ofthe service.
 18. A non-transitory machine-readable medium, comprisingexecutable instructions that, when executed by a processor, facilitateperformance of operations, comprising: receiving a request for a servicefrom a user equipment; identifying that the device is associated with afirst core environment comprising first core network equipment; andinitiating, on the user equipment, code representing the service,wherein the code is an implementation of the service associated with asecond core environment comprising second core network equipment. 19.The non-transitory machine-readable medium of claim 18, wherein theoperations further comprise determining, based on the request for theservice, that the user equipment has transitioned from being connectedto the second core network equipment of the second core environment tobeing connected to the first core network equipment of the first coreenvironment.
 20. The non-transitory machine-readable medium of claim 18,wherein a permissive service container comprising the code is cached toa group of network storage devices.